Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

use novendor param as flag for don't read vendro name, need for dexp ups #2839

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

crodar33
Copy link

@crodar33 crodar33 commented Mar 8, 2025

As I found, in hunnox_protocol on step 3 and asking_for = x0c it tried to read some string (vendor data by protocol), but ups didn't provide this data and because empty value on next step it cause crash of ups logic and it are stops response.
As I found, it should be solved by use novendor, that was used in blazer_usb, I added use it in nutdrv_qx, but not sure if it will not broke other working setup. Please suggest better solution for it.

@jimklimov
Copy link
Member

Looks reasonable, thanks. In the example you posted voltage overrides with floating-point separated by comma - should be by a dot. I can fix the commit here, but double-check that your running configuration does act as you expect it to :)

@jimklimov jimklimov added Qx protocol driver Driver based on Megatec Q<number> such as new nutdrv_qx, or obsoleted blazer and some others Incorrect or missing readings On some devices driver-reported values are systemically off (e.g. x10, x0.1, const+Value, etc.) impacts-release-2.8.2 Issues reported against NUT release 2.8.2 (maybe vanilla or with minor packaging tweaks) labels Mar 9, 2025
@jimklimov jimklimov added this to the 2.8.3 milestone Mar 9, 2025
…nd novendir in nutdrv_qx [networkupstools#2839]

Signed-off-by: Jim Klimov <jimklimov+nut@gmail.com>
…pstools#2839]

* Floating-point numbers are dot-separated
* Add the comment with a link to PR for details

Signed-off-by: Jim Klimov <jimklimov+nut@gmail.com>
@crodar33
Copy link
Author

hi, I have change settings locally, output of upsc dexp_nutdrv@localhost look like:

upsc dexp_nutdrv@localhost
Init SSL without certificate database
battery.charge: 87
battery.voltage: 27.0
battery.voltage.high: 28.6
battery.voltage.low: 21.4
device.type: ups
driver.debug: 0
driver.flag.allow_killpower: 0
driver.flag.norating: enabled
driver.flag.noscanlangid: enabled
driver.flag.novendor: enabled
driver.name: nutdrv_qx
driver.parameter.default.battery.voltage.high: 28.6
driver.parameter.default.battery.voltage.low: 21.4
driver.parameter.langid_fix: 0x0409
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.product: MEC0003
driver.parameter.productid: 0000
driver.parameter.protocol: hunnox
driver.parameter.subdriver: hunnox
driver.parameter.synchronous: auto
driver.parameter.vendorid: 0001
driver.state: quiet
driver.version: 2.8.2.2324-2324-ged967d659
driver.version.data: Hunnox 0.02
driver.version.internal: 0.41
driver.version.usb: libusb-0.1 (or compat)
input.frequency: 49.8
input.voltage: 241.0
input.voltage.fault: 0.0
output.voltage: 241.0
ups.beeper.status: disabled
ups.delay.shutdown: 60
ups.delay.start: 0
ups.load: 23
ups.productid: 0000
ups.status: OL
ups.temperature: 29.0
ups.type: online
ups.vendorid: 0001

@jimklimov jimklimov added the DDL label Mar 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DDL impacts-release-2.8.2 Issues reported against NUT release 2.8.2 (maybe vanilla or with minor packaging tweaks) Incorrect or missing readings On some devices driver-reported values are systemically off (e.g. x10, x0.1, const+Value, etc.) Qx protocol driver Driver based on Megatec Q<number> such as new nutdrv_qx, or obsoleted blazer and some others
Projects
Status: Todo
Development

Successfully merging this pull request may close these issues.

2 participants